code/addons/vitest/templates/vitest.config.template.ts (1)

12-17: ⚡ Quick win

Use a zero-argument BrowserCommand signature here.

Line 12 declares BrowserCommand<[number, number]>, but the command implementation takes only ctx and is called with no arguments (see commands.resetMousePosition() in the setup-file). The generic should be BrowserCommand<[]> to match the actual payload.

♻️ Proposed fix

-const resetMousePosition: BrowserCommand<[number, number]> = async (ctx) => {
+const resetMousePosition: BrowserCommand<[]> = async (ctx) => {
   if (ctx.provider.name !== 'playwright')
     throw new Error('resetMousePosition requires the Playwright provider');
   const frame = await ctx.frame();
   await frame.page().mouse.move(-1000, -1000);
 };

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@code/addons/vitest/templates/vitest.config.template.ts` around lines 12 - 17,
The BrowserCommand generic for resetMousePosition is incorrect: change its type
from BrowserCommand<[number, number]> to BrowserCommand<[]> so the command
signature matches its zero-argument implementation (resetMousePosition(ctx) is
invoked with no payload). Update the declaration of resetMousePosition to use
BrowserCommand<[]> and ensure any references or exports that rely on its type
reflect the new generic.

code/addons/vitest/src/vitest-plugin/setup-file.ts (1)

40-53: ⚡ Quick win

Remove unnecessary error handling and simplify the defensive check

Line 41's in operator is safe. The commands export is guaranteed to exist in both Vitest 3.x and 4.x, so the destructuring on Line 40 will always succeed. The catch block checking for "Cannot destructure property 'commands'" is dead code and can be removed. Simplify to safely check for the resetMousePosition method:

Proposed fix

 export const resetMousePositionBeforeTests = async () => {
   try {
     const { commands } = await import('vitest/browser');
-    if ('resetMousePosition' in commands && isFunction(commands.resetMousePosition)) {
+    if (isFunction(commands.resetMousePosition)) {
       await commands.resetMousePosition();
     }
   } catch (error) {
     // Ignore when vitest/browser is not found (Vitest 3)
     if (error instanceof Error && error.message.includes("Cannot find module 'vitest/browser'")) {
       return;
     }
-    // Ignore when commands is not exported by vitest/browser (Vitest 3)
-    if (
-      error instanceof Error &&
-      error.message.includes("Cannot destructure property 'commands'")
-    ) {
-      return;
-    }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@code/addons/vitest/src/vitest-plugin/setup-file.ts` around lines 40 - 53,
Remove the dead error check that looks for the "Cannot destructure property
'commands'" message in the catch block: keep the current dynamic import of
'vitest/browser' and the defensive runtime check for commands.resetMousePosition
(the in operator and isFunction(commands.resetMousePosition)), but delete the
entire conditional that tests error.message.includes("Cannot destructure
property 'commands'") so the catch only ignores missing-module errors and
otherwise rethrows or handles real errors; target the try/catch surrounding the
import and the symbols commands and resetMousePosition.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes